Method for the translation of programs for reconfigurable architectures

ABSTRACT

Data processing using multidimensional fields is described along with methods for advantageously using high-level language codes.

FIELD OF THE INVENTION

The present invention relates to optimal use of reconfigurable architectures and optimal execution of instructions in a given high-level language in reconfigurable architectures.

BACKGROUND INFORMATION

To implement execution of instructions for handling data (programs) that are written in high-level languages in a particular architecture used for data handling, there are conventional compilers which translate the instructions of the high-level language into instructions that are better adapted to the architecture used. Compilers which support highly parallel architectures in particular are thus parallelizing compilers.

Conventional parallelizing compilers normally use special constructs such as semaphores and/or other methods for synchronization. Technology-specific methods are typically used. Conventional methods are not suitable for combining functionally specified architectures with the particular dynamic response and imperatively specified algorithms. The methods used therefore yield satisfactory results only in special cases.

Compilers for reconfigurable architectures, in particular for reconfigurable processors, generally use macros created specifically for the intended reconfigurable hardware, mostly using hardware description languages such as Verilog, VHDL, or System C to create the macros. These macros are then called up from the program flow (instantiated) by an ordinary high-level language (e.g., C, C++).

There are conventional compilers for parallel computers which map program parts onto multiple processors on a coarse-grained structure, mostly based on complete functions or threads.

In addition, there are conventional vectorizing compilers which convert extensive linear data processing, such as computations of large expressions, into a vectorized form and thus permit computation on superscalar processors and vector processors (e.g., Pentium, Cray).

A method for automatic mapping of functionally or imperatively formulated computation procedures onto different target technologies is described here, in particular on ASICs, reconfigurable modules (FPGAs, DPGAs, VPUs, chess array, kress array, Chameleon, etc.; hereinafter combined under the term VPU), sequential processors (CISC-/RISC CPUs, DSPs, etc.; hereinafter summarized by the term CPU) and parallel computer systems (SMP, MMP, etc.). In this connection, reference is made in particular to the following patents and patent applications by the present applicant: P 44 16 881.0-53, DE 197 81 412.3, DE 197 81 483.2, DE 196 54 846.2-53, DE 196 54 593.5-53, DE 197 04 044.6-53, DE 198 80 129.7, DE 198 61 088.2-53, DE 199 80 312.9, PCT/DE 00/01869, DE 100 36 627.9-33, DE 100 28 397.7, DE 101 10 530.4, DE 101 11 014.6, PCT/EP 00/10516, EP 01 102 674.7, PACT13, PACT17, PACT18, PACT22, PACT24, PACT25, PACT26US, PACT02, PACT04, PACT08, PACT10, PACT15, PACT18(a), PACT27, PACT19. Each of these are hereby fully incorporated herein by reference for disclosure purposes.

VPUs are basically composed of a multidimensional, homogeneous or inhomogeneous, flat or hierarchical array (PA) of cells (PAEs) which are capable of executing any functions, in particular logic functions and/or arithmetic functions and/or memory functions and/or network functions. PAEs are typically assigned a loading unit (CT) which determines the function of the PAEs by configuration and optionally reconfiguration.

This method is based on an abstract parallel machine model which in addition to the finite automaton also integrates imperadve problem specifications and permits an efficient algorithmic derivation of an implementation on different technologies.

The following compiler classes are conventional:

Classical compilers, which often generate stack machine code and are suitable for very simple processors, which are essentially designed as normal sequencers (see N. Wirth, Compilerbau [Compiler Design], Teubner Verlag).

Vectorizing compilers construct mostly linear code which is intended for special vector computers or for highly pipelined processors. These compilers were originally available for vector computers such as the Cray. Modern processors such as Pentium processors require similar methods because of the long pipeline structure. Since the individual computation steps are performed as vectorized (pipelined) steps, the code is much more efficient. However, the conditional jump means problems for the pipeline. Therefore, a jump prediction which assumes a jump destination is appropriate. If this assumption is incorrect, however, the entire processing pipeline must be deleted. In other words, each jump for these compilers is problematical and actually there is no parallel processing. Jump predictions and similar mechanisms require a considerable extra complexity in terms of hardware.

There are hardly any coarse-grained parallel compilers in the actual sense, parallelism typically being marked and managed by the programmer or the operating system, e.g., it is usually performed on a thread level in MMP computer systems such as various IBM architectures, ASCI Red, etc. A thread is a largely independent program block or even a separate program. Therefore, threads are easily parallelized on a coarse-grained level. Synchronization and data consistency must be ensured by the programmer or the operating system. This is complex to program and requires a significant portion of the computation power of a parallel computer. In addition, only a fragment of the parallelism which is actually possible is in fact usable due to this coarse parallelization.

Fine-grained parallel compilers (e.g., VLIW) attempt to map the parallelism in a fine-grained form into VLIW arithmetic means that are capable of executing a plurality of computation operations in one clock cycle but may have a common register set. This limited register set is a significant problem because it must provide the data for all the computation operations. In addition, the data dependencies and inconsistent read/write operations (LOAD/STORE) make parallelization difficult. Reconfigurable processors have a large number of independent arithmetic units, typically located in a field. These are typically interconnected by buses instead of by a common register set. Therefore, vector arithmetic units are easily constructed, while it is also possible to perform simple parallel operations. In contrast with traditional register concepts, data dependencies are resolved by the bus connections.

SUMMARY

According to an example embodiment of the present invention, concepts of vectorizing compilers and parallelizing compilers (e.g., VLIW) are used at the same time for a compiler for reconfigurable processors and thus vectorization and parallelization are performed on a fine-grained level.

An advantage is that the compiler need not map onto a fixedly predetermined hardware structure, but instead the hardware structure may be configured using an example method according to the present invention so that it is optimally suitable for mapping the particular compiled algorithm.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 a shows the design of an ordinary finite automaton in which a combinatory network (0101) is linked to a register.

FIG. 1 b shows a representation of the finite automaton by a reconfigurable architecture.

FIG. 2 shows the mapping of a finite automaton onto a reconfigurable architecture.

FIGS. 3 a-3 c shows different aspects for handling variables.

FIGS. 4 a-4 b shows implementations of loops.

FIG. 5 a shows the iterative computation of

  FOR i:=1 TO 10  x1 := x1 * x1;

FIG. 5 b shows the rolling out of the computation of

  FOR i:=1 TO 10  x1 := x1 * x1;

FIG. 6 shows the execution of a WHILE loop according to FIG. 4 b over several configurations.

FIG. 7 a shows how many ILPs may be achieved at a certain stage within the data flow graph.

FIG. 7 b shows mapping onto five arithmetic means.

FIG. 7 c shows processing in one arithmetic means.

FIG. 8 a shows the graph of FIG. 7 a mapped onto a group of PAEs.

FIG. 8 b shows sets of operations that are not parallel.

FIG. 8 c shows vectorization is impossible, but PAR(p) is high.

FIG. 8 d shows the graphs according to FIG. 7 a in the case where there is no parallelism.

FIG. 9 a shows the same function in which certain paths are executable simultaneously.

FIG. 9 b shows an example in which vectorization is not possible.

2. DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

A finite automaton is used as the basis for executing practically any method for specifying algorithms. The structure of a finite automaton is shown in FIG. 1. A simple finite automaton is broken down into a combinatory network and a register stage for temporary storage of data between the individual data processing cycles.

A finite automaton executes a number of purely combinatory data manipulations (i.e., logic and/or arithmetic manipulations, for example) and then reaches a stable state which is represented in a register (set). Based on this stable state, a decision is made as to which next state is to be reached in the next processing step and thus also which combinatory data manipulations are to be performed in the next step.

For example, a finite automaton is represented by a processor or sequencer. In a first processing step, subtraction of data may be performed. The result is stored. In the next step, a jump may be performed, based on the result of the subtraction, resulting in further processing, depending on the plus or minus sign of the result.

The finite automaton permits mapping of complex algorithms onto any sequential machines, as illustrated in FIG. 2. The complex finite automaton depicted here is made up of a complex combinatory network, a memory for storing data, and an address generator for addressing the data in the memory.

Any sequential program may fundamentally be interpreted as a finite automaton, but usually the result is a very large combinatory network. In programming classical “von Neumann” architectures—i.e., with all CPUs—the combinatory operations are therefore broken down into a sequence of simple individual fixedly predetermined operations (opcodes) on CPU-internal registers. This breakdown results in states for control of the combinatory operation, which is broken down into a sequence, but these states are not present per se within the original combinatory operation or are not required. Therefore, however, the states of a von Neumann machine that are to be processed differ fundamentally from the algorithmic states of a combinatory network, i.e., from the registers of finite automatons.

It has now been recognized that the VPU technology (such as that described by some or all of the publications PACT01, PACT02, PACT03, PACT04, PACT05, PACT08, PACT10, PACT13, PACT17, PACT18, PACT22, PACT24, which are herewith fully incorporated into the present patent application through this reference) in contrast with the rigid opcodes of CPUs makes it possible to compile complex instructions according to an algorithm to be mapped, as in flexible configurations.

2.1 The Compiler's Mode of Operation

In the mode of operation of the compiler, it may be particularly advantageous if the complex instructions are generated so that they are executed in the PAE matrix for the longest possible period of time without reconfiguration.

In addition, the compiler generates the finite automaton preferably from the imperative source text in such a way that it is particularly well adapted to the particular PAE matrix, i.e., operations which typically use coarse-grained logic circuits (ALUs, etc.), if necessary also fine-grained elements that are also present (FPGA cells in the VPU, state machines, etc.) particularly efficiently, are provided.

The compiler-generated finite automaton is then broken down into configurations.

The processing (interpretation) of the finite automaton is performed on a VPU in such a way that the generated configurations are mapped successively onto the PAE matrix and the operating data and/or states which are to be transmitted between the configurations are filed in the memory. The method described in PACT04 and/or the corresponding architecture may be used to this end. This memory is determined or provided by the compiler. A configuration here represents a plurality of instructions; at the same time, a configuration determines the operation of the PAE matrix for a plurality of cycles, and during these cycles a certain amount of data is processed in the matrix. This data comes from a VPU-external source and/or an internal memory and is written to an external source and/or an internal memory. The internal memories here replace the register set of a CPU according to the related art in such a way that, for example, a register is represented by a memory so that instead of one data word per register, a full data set is stored per memory.

The data and/or states of the processing of a configuration that is running may be filed in the memory in a manner determined by the compiler and are thus available for the next configuration to be run.

A significant difference from compilers which parallelize on the basis of instructions is thus that the method configures and reconfigures the PAE matrix in such a way that a configured sequence of combinatory networks is emulated on a VPU while traditional compilers combine loaded sequences of instructions (opcodes); in this case, an instruction may be considered a combinatory network.

2.2 Exemplary Embodiment WHILE Language

The functioning of the compiler is illustrated below on the basis of a simple language as an example. This assumes a language the principles of which are already known, but a known publication [e.g., “Armin Nückel dissertation”] describes only the mapping of a function onto a static combinatory network, whereas in accordance with the present invention, the mapping is performed onto configurations which are then mapped onto the PAE matrix in a chronological order according to the algorithm and the states that result during processing.

The programming language assumes that there exists a “WHILE” instruction in addition to simple logical and/or arithmetic links, and this instruction is defined by the following syntax:

-   -   WHILE . . .

Possible constructs are thus: Instruction

-   -   Sequence of instructions     -   Loop

An instruction or a sequence of instructions is mappable onto a combinatory network using the compiler method described here.

FIG. 3 a shows a combinatory network and the pertinent variables. The content of one and the same variable (e.g., x1) may change from one step (0301) of the network to the next step (0302).

This change is depicted in FIG. 3 b for the assignment

  x1 := x1 + 1.

For addressing for reading the operands and for storing the results, address generators may now be synchronized with the combinatory network of the assignment. With each variable processed, corresponding new addresses are generated for operands and results (FIG. 3 c). In principle, any type of address generator may be used, depending on the addressing schemes of the compiled application. Shared, combined, or completely independent address generators may be implemented for operands and results.

Typically a plurality of data is processed within a certain configuration of PAEs in the data processing as in the present data processing model. Therefore, the compiler is preferably designed for the simple FIFO mode which is possible in many if not most applications and is applicable at least for the data memories, which are used within this description for storing data and states of the data processing (more or less as a replacement for a traditional register set of conventional CPUs). In other words, memories are used for temporary storage of variables between configurations. Here again, a configuration is like an instruction of a normal processor, and the memories (in particular a plurality of memories) are comparable to the register set of a normal processor.

2.2.3 Sequences of Instructions

A sequence of the exemplary assignment may be generated as follows (FIG. 4 a):

  x l := 0; WHILE TRUE DO  x1 := x1 + 1;

This sequence may now be mapped via an assignment according to 2.2.1 and address generators for operands and results.

Finite Sequences

For the sake of thoroughness, a particular embodiment of sequences apart from the defined constructs of the WHILE language will now be discussed. A finite sequence of the exemplary assignment may be generated as follows:

  FOR i := 1 TO 10 x1 := X1 + 1;

Such a sequence may be implemented by two methods:

-   a) By generating an adder for computing i according to the WHILE     construct (see 2.2.4) and another adder for computing x1. The     sequence is mapped as a loop and is computed iteratively (FIG. 5 a). -   By rolling out the loop, so that the computation of i as a function     is eliminated. The computation of x1 is instantiated i times and is     constructed as a pipeline, resulting in i adders connected in series     (FIG. 5 b).

2.2.4 Conditions

Conditions may be expressed via WHILE. For example:

  x1 := 0; WHILE x1 < 10 DO x1 := x1 +1;

The mapping generates an additional PAE for processing the comparison. The result of the comparison is represented by a status signal (see, e.g., Trigger described in PACT08), which is analyzed by the PAEs processing the instruction and the address generators.

FIG. 4 b shows the resulting mapping.

By analyzing the condition (WHILE here, in general and reasonably also other instructions such as IF; CASE implementable), a status is generated which may be made available to the subsequent data processing (DE 197 04 728.9) and/or may be sent to the CT or a local load control (DE 196 54 846.2) which then derives information therefrom regarding the further program flow and any pending reconfigurations

2.2.5 Basic Method

According to the previous method, each program is mapped into a system having the following structure:

-   1. Memory for operands (comparable to the register of a CPU) -   2. Memory for results (comparable to the register of a CPU) -   3. Network of a) assignments and/or b) compare instructions, i.e.,     conditions such as IF, CASE, loops (WHILE, FOR, REPEAT) -   4. Optional address generator(s) for triggering the memories     according to 1 and 2.

2.2.6 Handling of States

For the purposes of the compiler described here, a distinction is now made between states that are relevant to the algorithm and those that are not. States are usually depicted in the VPU technology by status signals (e.g., trigger in PACT08) and/or handshakes (e.g., RDY/ACK in PACT02). In general, states (in particular in other technologies, e.g., FPGAs, DPGAs, Chameleon modules, Morphics, etc.) may be represented by any signals, signal bundles and/or registers. The compiler method described here may also be applied to such technologies, although important parts of the description are preferentially focused on the VPU.

Relevant states are necessary within the algorithm to describe its correct function. They may be important for the algorithm.

Irrelevant states occur due to the hardware used and/or the selected mapping or for other secondary reasons. They are thus may be essential for the mapping (i.e., the hardware).

Only the relevant states must be obtained with the data. Therefore, these states are filed together with the data in the memories because they occur with the data either as a result of the processing or they are necessary as operands with the data for the next processing cycle.

Irrelevant states, however, are necessary only locally and/or chronologically locally and therefore need not be stored.

Example

-   a) The state information of a comparison is relevant for further     processing of data because it determines the functions to be     executed. -   b) It is assumed that a sequential divider is formed, e.g., by     mapping a division instruction onto hardware which supports only     sequential division. This results in a state which characterizes the     computation step within the division. This state is irrelevant     because only the result (i.e., the division that is performed) is     necessary for the algorithm. Thus, only the result and the time     information (i.e., the availability) are required in this case. The     compiler preferably differentiates between such relevant and     irrelevant states.

The time information is accessible, for example, via the RDY/ACK handshake in VPU technology described in PACT01, 02, 13. However, it should be pointed out here that the handshake also does not represent a relevant state because it only signals the validity of the data so this in turn reduces the remaining relevant information to the existence of valid data.

2.2.7 Handling of Time

In many programming languages, in particular in sequential languages such as C, an exact chronological sequence is determined implicitly by the language. In sequential programming languages, this is accomplished, for example, by the sequence of individual instructions. If this is required by the programming language and/or the algorithm, the compiler method is executed in such a way that the time information may be mapped onto synchronization models such as RDY/ACK and/or REQ/ACK or a time stamp method described in German Patent Application No. DE 101 10 530.4.

In other words, the implicit time information of sequential languages is mapped into a handshake protocol in such a way that the handshake protocol (RDY/ACK protocol) transmits the time information and in particular ensures the sequence of instructions.

For example, the following FOR loop is run and iterated only when the variable inputstream is acknowledged using a RDY for each run. If there is no RDY, the loop run is stopped until RDY arrives.

  while TRUE s := 0 for i := 1 to 3 s := s + inputstream;

The property of sequential languages of being controlled only by instruction processing is thus linked during compiling to the data flow principle to control the processing through the data stream, i.e., the existence of data. In other words, a command and/or an instruction (e.g., s:=s+inputstream;) is processed only when the operation may be executed and the data is available.

It is noteworthy that this method does not usually result in any change in the syntax or semantics of a high-level language. Thus, existing high-level language code may be brought to execution on a VPU without problems by recompiling.

2.2.8 Loading and Storing Data

For the principles of the load/store operations, the following is noteworthy.

The following types of addressing are treated differently:

-   1. External addressing, i.e., data transfers using external modules -   2. Internal addressing, i.e., data transfer between PAEs, in     particular between RAM PAEs and ALU PAEs.

Furthermore, special attention should be devoted to chronological decoupling of data processing and data loading and storing.

Bus transfers are broken down into internal and external transfers.

bt1) External read accesses (load operations) are separated, and in one possible embodiment, they are also preferentially translated into a separate configuration. The data is transferred from an external memory to an internal memory. bt2) Internal accesses are linked to the data processing, i.e., the internal memories (register operation) are read and/or written to for the data processing. bt3) External write accesses (store operation) are separated, i.e., in a preferred possible embodiment they are also translated into a separate configuration. The data is transferred from an internal memory to an external memory.

It is essential that bt1, bt2 and bt3—i.e., loading the data (load), processing the data (data processing and bt2) and writing the data (bt3)—may be translated into different configurations which may, if necessary, be executed at a different point in time.

This method will now be illustrated on the basis of the following:

  function example (a, b : integer) → x : integer for i := 1 to 100 for j := 1 to 100 x[i] := a[i] * b[j]

This function may be transformed by the compiler into three parts, i.e., configurations (subconfig):

example#dload: loads the data from external memories, peripherals, etc. and writes it into internal memories. Internal memories are identified by r# and the name of the original variable. example#process: corresponds to the actual data processing. It reads the data out of internal operands and writes the results back into internal memories. example#dstore: writes the results from the internal memories to external memories, peripherals, etc.

  function example# (a, b : integer) → x : integer subconfig example#dload for i := 1 to 100  r#a[i] := a[i] for j :=1 to 100  r#b[j] := b[j] subconfig example#process for i := 1 to 100 for j := 1 to 100  r#x[i] := r#a[i] * r#b[j] subconfig example#dstore for i := 1 to 100  x[i] := r#x[i]

One effect of this method is that instead of i*j=100 *100=10,000 external accesses, only i+j=100+100=200 external accesses are executed to read the operands. These accesses are also completely linear, which greatly speeds up the transfer rate with today's bus systems (burst) and/or memories (SDRAM, DDRAM, RAMBUS, etc.).

The internal memory accesses are performed in parallel because different memories have been assigned to the operands.

For writing the results, i=100 external accesses are necessary and these may also be performed again linearly with maximum performance.

If the number of data transfers is not known in advance (e.g., WHILE loop) or is very large, a method that reloads the operands as needed through subprogram calls and/or which writes the results externally may be used. In a preferred embodiment, the states of the FIFOs may (also) be queried: ‘empty’ when the FIFO is empty and ‘full’ when the FIFO is full. The program flow responds according to the states. It should be pointed out that certain variables (e.g., ai, bi, xi) are defined globally. For performance optimization, a scheduler may execute the configurations example#dloada, example#dloadb even before the call of example#process according to the methods already described, so that data is already preloaded. Likewise, example#dstore(n) may also be called up after termination of example#process in order to empty r#x.

  subconfig example#dloada(n)  while !full(r#a) AND ai<=n r#a[ai] := a[ai] ai++ subconfig example#dloadb(n)  while !full(r#b) AND bi<=n r#b[bi] := b[bi] bi++ subconfig example#dstore(n)  while !empty(r#x) AND xi<=n x[xi] := r#x[xi] xi++ subconfig example#process  for i := 1 to n for j := 1 to m  if empty(r#a) then example#dloada(n)  if empty(r#b) then example#dloadb(m)  if empty(r#x) then example#dstore(n)  r#x[i] := r#a[i] * r#b[j] bj := 1

The subprogram calls and the management of the global variables are comparatively complex for reconfigurable architectures. Therefore, in a preferred embodiment, the following optimization may be performed, in which all the configurations are running largely independently and terminate after complete processing. Since the data b[j] is needed repeatedly, example#dloadb must be run several times accordingly. Two alternatives are presented for this as an example:

Alternative 1: example#dloadb terminates after each run and is reconfigured by example#process for each restart. Alternative 2: example#dloadb runs infinitely and is terminated by example#process.

A configuration is inactive (waiting) during ‘idle.’

  subconfig example#dloada(n)  for i := 1 to n while full(r#a)  idle r#a[i] := a[i]  terminate subconfig example#dloadb(n) while 1 // ALTERNATIVE 2  for i := 1 to n while full(r#b)  idle r#b[i] := a[i]  terminate subconfig example#dstore(n)  for i := 1 to n while empty(r#b)  idle x[i] := r#x[i]  terminate subconfig example#process  for i := 1 to n for j := 1 to m  while empty(r#a) or empty(r#b) or full (r#x) idle  r#x[i] := r#a[i] * r#b[j] config example#dloadb(n) // ALTERNATIVE 1 terminate example#dloadb(n) // ALTERNATIVE 2 terminate

To prevent waiting cycles, configurations may also be terminated as soon as they are temporarily unable to continue fulfilling their function. The corresponding configuration is removed from the reconfigurable module but it remains in the scheduler. The instruction ‘reenter’ is used for this purpose below. The relevant variables are saved before termination and are restored in the repeated configuration:

  subconfig example#dloada(n)  for ai := 1 to n if full(r#a) reenter r#a[ai] := a[ai]  terminate subconfig example#dloadb(n)  while 1 // ALTERNATIVE 2 for bi := 1 to n  if full(r#b) reenter  r#b[bi] := a[bi]  terminate subconfig example#dstore(n)  for xi := 1 to n if empty(r#b) reenter x[xi] := r#x[xi]  terminate subconfig example#process  for i := 1 to n for j := 1 to m  if empty(r#a) or empty(r#b) or full (r#x) reenter  r#x[i] := r#a[i] * r#b[j] config example#dloadb(n) // ALTERNATIVE 1 terminate example#dloadb(n) // ALTERNATIVE 2 terminate

2.3 Macros

More complex functions of a high-level language such as loops are typically implemented by macros. The macros are therefore preselected by the compiler and are instantiated at translation time (see FIG. 4).

The macros are either constructed from simple language constructs of the high-level language or they are constructed at the assembler level. Macros may be parameterized to permit simple adaptation to the algorithm described (see FIG. 5, 0502). In the present case, the macros are also to be incorporated.

2.4 Feedback Loops and Registers

Undelayed feedback loops may occur within the mapping of an algorithm into a combinatory network and may oscillate in an uncontrolled manner.

In VPU technologies implemented in practical terms according to PACT02, this is prevented by a construct of the PAE in which at least one register is defined for decoupling, more or less fixedly in the PAEs.

In general, undelayed feedback loops are discernible through graphic analysis of the resulting combinatory network. Registers are then deliberately inserted for separation into the data pathways in which there is an undelayed feedback loop. The compiler may thus manage register means, i.e., memory means.

Due to the use of handshake protocols (e.g., RDY/ACK according to 2.2.7), the correct function of the computation is also ensured by the insertion of registers.

2.5 Processor Model/Time Domain Multiplexing (TDM)

Basically, each PAE matrix implemented has virtually only one finite variable. In the following step, a partitioning of the algorithm according to section 2.2.5 paragraph 4 a/13 into a plurality of configurations, which are configured one after the other into the PAE matrix, must therefore be performed. The goal is typically to compute the largest possible number of data packets in the network without having to perform a reconfiguration.

Between configurations, a temporary storage is performed, with the buffer memory—similar to a register in the case of CPUs—storing the data between the individual configurations that are executed sequentially.

A sequential processor model is thus created by reconfiguring configurations, data processing in the PAE matrix, and temporary storage in the memories.

In other words, due to the compiling described here, instead of an opcode, complex configurations are executed sequentially in VPU technology. While in the case of CPUS, an opcode typically processes a data word, in VPU technology a plurality of data words (a data packet) is processed by a configuration. The efficiency of the reconfigurable architecture is therefore increased due to a better ratio between reconfiguration complexity and data processing.

At the same time, instead of a register, a memory is used in VPU technology because instead of processing data words, data packets are processed between configurations.

This memory may be designed as a random access memory, a stack, a FIFO or any other memory architecture, although a FIFO is typically the best and the simplest option to be implemented.

Data is then processed by the PAE matrix according to the configured algorithm and is stored in one or more memories. The PAE matrix is reconfigured after processing a volume of data and the new configuration takes the intermediate results from the memory (memories) and continues the execution of the program. New data may then of course be incorporated into the computation from external memories and/or the periphery and likewise results may be written to external memories and/or the periphery.

In other words, the typical sequence in data processing is read-out from internal RAMs, processing the data in the matrix and writing data to the internal memories, and any external sources, or targets for the data transfer may be used additionally to or instead of the internal memories for data processing.

Although “sequencing” in CPUs is defined as reloading of an opcode, “sequencing” of VPUs is therefore defined as (re)configuring configurations according to what was said above. However, this does not mean that under certain conditions, parts of the field may not be operated as a sequencer in the conventional sense.

The information as to when and/or how sequencing is performed, i.e., which next configuration is to be configured, may be represented by various pieces of information which may be used individually or in combination. For example, the following strategies are appropriate for deriving the information either alone and/or in combination, i.e., alternatively:

-   a) defined by the compiler at translation time; -   b) defined by the event network (trigger, DE 197 04 728.9), where     the event network may represent internal and/or external states; -   c) by the degree of filling of the memories (trigger, DE 197 04     728.9, DE 196 54 846.2-53).

2.5.1 Influence of the TDM on the Processor Model

Partitioning of the algorithm determines to a significant extent the relevant states which are filed in the memories between the various configurations. If a state is relevant only within a configuration (locally relevant state), it is not necessary to store it, which is taken into account preferentially by the compiler method.

For the purposes of debugging the program to be executed, however, it may nevertheless be expedient to store these states to permit that they are accessed by the debugger. Reference is made to German Patent Application No. DE 101 42 904.5, which is herewith incorporated to the full extent for disclosure purposes.

Furthermore, additional states may become relevant when using a task switch mechanism (e.g., by an operating system or interrupt sources) and the configurations being executed currently are interrupted, other configurations are loaded and/or the aborted reconfiguration is to be resumed at a later point in time. A detailed description follows in the section below.

A simple example should show a differentiating factor for locally relevant states:

-   a) A branching of the type “if ( ) then . . . else . . . ” fits     completely into a single configuration, i.e., both data paths     (branches) are mapped jointly completely within the configuration.     The state that is obtained in the comparison is relevant, but     locally relevant, because it is no longer needed in the following     configurations. -   b) The same branching is too large to fit completely into a single     configuration. Multiple configurations are necessary to map the     complete data paths. In this case, the status is globally relevant     and must be stored and assigned to the particular data because the     subsequent configurations require the particular state of the     comparison in further processing of the data.

2.6 Task Switching

The possible use of an operating system has an additional influence on the consideration and handling of states. Operating systems use task schedulers, for example, to manage multiple tasks to make multitasicing available.

Task schedulers interrupt tasks at a certain point in time, and start other tasks, and after processing these other tasks, they resume further processing of the interrupted task.

If it is ensured that a configuration—which may correspond here to processing a task—is terminated only after being completely processed, i.e., when all the data and states to be processed within this configuration cycle have been stored—then locally relevant states may remain unstored. This method, i.e., complete processing of a configuration and the subsequent task switching, is the preferred method for operating reconfigurable processors and corresponds essentially to the sequence in a normal processor which first completes the assignments currently being processed and then changes tasks.

For many applications, however, a particularly prompt response to a task change request is necessary, e.g., in realtime applications. It may be expedient here to abort configurations before they are completely processed.

If the task scheduler aborts configurations before they are completely processed, local states and/or data must be saved. This is also advantageous when the processing time of a configuration is not predictable. In conjunction with the known halting problem and the risk that a configuration may not be terminated at all, e.g., due to an error, this also seems appropriate to prevent the entire system from being deadlocked. Therefore, in the present case, relevant states are also to be regarded as including those that are necessary for a task change and a renewed correct resumption of data processing, taking into account task switching.

In task switching, the memory for results is thus to be saved and, if necessary, the memory for operands is also to be saved and restored at a later point in time, i.e., when resuming this task. This may be performed in a manner comparable to that used with PUSH/POP instructions and conventional methods. In addition, the state of data processing must be saved, i.e., the pointer at the last operand processed completely. Reference is made here to PACT18 in particular.

Depending on the optimization of task switching, there are two possibilities here, for example:

a) The aborted configuration is reconfigured and only the operands are loaded. Data processing thus begins anew as if processing of the configuration had not yet begun. In other words, all data computations are simply executed from the beginning, even if some computations have been performed previously. This option is simple but not efficient. b) The aborted configuration is reconfigured, with the operands and the results already computed being loaded into the particular memory. Data processing continues with operands that have not been computed completely. This method is much more efficient but presupposes that additional states which occur during processing of the configuration may become relevant, e.g., if at least one pointer, pointing to the last operands completely computed, must be saved, so that after a successful reconfiguration, their successors may be reset.

2.7 Context Switching

A particularly preferred variant for managing relevant data is made available through the context switching described below. In task switching and/or in execution of configurations and switching configurations (see, for example, German Patent Application No. DE 102 06 653.1, which is herewith incorporated to the full extent for disclosure purposes), it may be necessary to save data or states which are typically not saved in the memory together with the operating data, because they only mark an end value, for a subsequent configuration.

The context switching which is implemented preferentially according to the present invention is performed in such a way that a first configuration is removed and the data to be saved remains in the corresponding memories (REGs) (memories, registers, counters, etc.).

A second configuration which connects the REG to one or more global memories in a suitable manner and in a defined sequence may then be loaded.

The configuration may use address generators, for example, to access the global memory (memories). It is therefore not necessary to first have each individual memory location defined by the compiler and/or to access REGs embodied as memories.

According to the configured connection between REGs, the contents of the REGs are written in a defined sequence into the global memory, the particular addresses being preselected by address generators. The address generator generates the addresses for the global memory or memories so that the memory areas written (PUSH AREA) may be unambiguously assigned to the first configuration that has been removed.

Different address spaces are thus preferentially provided for different configurations. The configuration here corresponds to a PUSH of ordinary processors.

Other configurations then use the resources.

Now the first configuration is to be restarted. First, a third configuration, which interconnects the REGs of the first configuration in a defined sequence, is started.

The configuration may in turn use address generators, for example, to access the global memory or memories and/or to access REGs embodied as memories.

An address generator preferably generates addresses so that the PUSH AREA assigned to the first configuration is accessed correctly. The generated addresses and the configured sequence of the REGs are such that the data in the REGs is written from the memories into the REGs in the original order. This configuration corresponds to a POP of ordinary processors.

The first configuration is then restarted.

In summary, a context switch is preferably performed in such a way that by loading particular configurations, which operate like PUSH/POP of known processor architectures, data to be saved is exchanged with a global memory. This data exchange via global memories using PUSH/POP exchange configurations is regarded as being particularly relevant.

This function is to be illustrated in an example: A function adds two rows of numbers; the length of the rows is not known at translation time and is only known at run time.

  proc example  while i<length do x[i] = a[i] + b[i] i = i +1

The function is then interrupted during its execution, e.g., by a task switch or because the memory provided for x is full; a, b, x are at this point in time in memories according to the present invention; however, i, and possibly length, must be saved.

To do so, the configuration “example” is terminated, with the register contents being saved and a PUSH configuration being started, and with i and length being read out of the registers and written to a memory.

  proc push  mem[<push_adr_example>] = i  push_adr_example++  mem[<push_adr_example>] = length

After execution, PUSH is terminated and the register contents may be deleted.

Other configurations are executed. After a period of time, the configuration “example” is restarted.

First a configuration “POP” is started, reading the register contents out of the memory again.

  proc pop  i = mem[<push_adr_example>]  push_adr_example++  length =mem[<push_adr_example>]

After execution, POP is terminated and the register contents are kept. The configuration “example” is restarted.

2.8 Algorithmic Optimization

Control structures are separated from algorithmic structures by the translation method described here. For example, a loop is broken down into a body (WHILE) and an algorithmic structure (instructions).

The algorithmic structures are preferably optionally optimizable by an additional tool downstream from the separation.

For example, downstream algebra software may optimize and minimize the programmed algorithms. These tools are known by such names as AXIOM, MARBLE, etc., for example. A more rapid execution of the algorithm and/or a substantially reduced space requirement may be achieved by minimization.

The result of the optimization is then sent back to the compiler and processed further accordingly.

It should also be pointed out that modern compilers (front ends) have already implemented a number of optimizations for algorithms (including in some cases algebraic optimizations) which are of course still usable as part of the method described here.

It should be pointed out explicitly that the example method described here, in particular section 2.2.7 “Handling of time” and section 2.3 “Macros,” may also be applied to compilers according to PACT20. PACT20 is expressly incorporated herewith by reference in the present patent application to the full extent for disclosure purposes.

3. APPLICABILITY FOR PROCESSORS ACCORDING TO THE RELATED ART, IN PARTICULAR HAVING A VLIW ARCHITECTURE

It should be pointed out in particular that instead of a PAE matrix, a system of arithmetic logic units (ALUs) according to the related art, such as those conventionally used in VLIW processors and/or a system of complete processors such as those conventionally used in multiprocessor systems, may be used, for example. The use of a single ALU constitutes a special case here, so that this method is also applicable for natural CPUs.

A method which permits translation of the WHILE language into semantically correct finite automatons was developed in the dissertation [see, e.g., dissertation of Armin Nückel]. In addition, a finite automaton may be used as a “subprogram” and vice-versa. This yields the possibility of mapping a configuration onto different implementation technologies such as CPUs, symmetrical multiprocessors, FPGAs, ASICs, VPUs.

In particular, it is possible to assign optimally suitable hardware to parts of an application and/or to determine a particular suitability and assign optimum hardware on the basis of the better or worse suitability. Preferably temporary distribution and reservation of resources may also be detectable. In other words, for example, a data flow structure would be assigned to a data flow architecture, while a sequential structure is mapped onto a sequencer if these are available and/or present.

The resulting problems of the resource assignments for the individual algorithms may be solved, e.g., by a “job assignment” algorithm for managing the assignment.

4. IMPLEMENTATION

The implementation of a compiler according to the present invention should be based on a “normal” sequential programming language such as C or Pascal. These languages have the property that due to their sequential character, a chronological sequence is implicitly and artificially generated due to the language definition per se.

Example A

  Line 1:i++ Line 2:a = i * b Line 3:x = p B a Line 4:j = i * i

The language definition fixedly predetermines that line 1 is executed before line 2 before line 3 before line 4. However, line 4 could also be executed directly after line 1 and thus simultaneously with lines 2 and 3.

In other words, through sequential languages, additional artificial and not algorithmically determined states are incorporated. Only the correct chronological sequence of the computations in example A is important. Line 4 must not be computed until i is correctly defined, i.e., after the processing of line 1. Line 2 also must not be processed until after the correct definition of i (i.e., after processing line 1). Line 3 requires the results of line 2 (variable a) and therefore may not be computed until after correct definition of variable a. This results in a data dependence but no particular states.

On the basis of the data dependencies of variable a in lines 2 and 3 (line 3 uses a as an operand; a is the result of line 2), the following transformation may thus be performed automatically by the compiler for representation of the parallelizability and/or vectorizability (ParVec transformation):

  Line 2: VEC{a = i * b; Line 3:   x = p − a}

VEC means that each term separated by ‘;’ is processed in succession; the terms inside the braces may basically be pipelined. Preferably all computations must be performed at the end of VEC{ } and concluded so that data processing is continued downstream from the VEC.

In an internal representation of the data structures in the compiler, the two computations are preferably marked as a vector:

  VEC{a=i*b; x=p−q}

Line 4 yields a simple vector:

  VEC{j = i*i}

Since line 4 may be computed at the same time as lines 2 and 3, the parallelism may be expressed as follows:

  PAR{{VEC{a=i*b; x=p−a}; VEC{j=i*i}}

PAR means that each term separated by ‘ . . . ’ may be processed at the same time. Preferably all computations must be performed and concluded at the end of PAR{ } so that data processing is continued downstream from PAR.

If line 1 is included, this yields:

  VEC{i++; PAR{{VEC{a=i*b; x=p−a}}{VEC{j=i*i}}}}

Since VEC{j=i*i} represents a vector having only one element, it may also be written as follows:

  VEC{i++; PAR{{VEC{a=i*b; x=p−a}}{j=i*i}}}

Another example shows a real state.

Example B

  Line 1:i++ Line 2:a = i * b Line 3:if a < 100 { Line 4:x = p B a Line 5:} else { Line 6:j = i*i }

Line 6 may now be executed only after the computation of lines 2 and 3. Lines 4 and 6 are computed alternatively. The state of line 3 is thus relevant for further data processing (relevant state).

Conditional states may be expressed by IF in the case of a transformation:

Lines 1-2: VEC{i++; a=i*b} Line 3: IF{{a<100}{line4}{line 6}} Line 4: VEC{x=p−a} Line 6; VEC{j=i*i}

In summary, this yields

  VEC{i++; a=i*b; IF{{a<100}{VEC{x=p−a}}{VEC{j=i*i}}}}

Other relevant states are generated by looping:

Example C

Line 1: for (i = 1, i < 100, i++) Line 2: a = a * i Line 3: q = p / a

Line 3 may be executed only after the loop has been terminated. There are thus relevant states in the case of conditional jumps.

A first transformation of the loop yields:

Line 1: i=1; Line 2: loop: if i >= 100 then exit Line 3: a = a * i Line 4: i++ Line 5: jump loop Line 6: exit: q = p / a

Lines 3 and 4 may be computed in parallel because line 4 does not depend on the result of line 3:

  PAR{{a=a*i}{i++}}

Line 5 yields a vector with the generated PAR because only after complete computation of values is it possible to jump back into the loop (so there is a time dependence here).

  VEC{PAR{{a=a*i}{i++}}; jump loop}

This yields the following for the condition:

loop: IF{{i>=100}{jump exit}{VEC{PAR{{a=a*i}{i++}}; jump loop}}}

Line 1 is a vector with the condition since it must be executed before the condition (IF uses i as an operand; i is the result of line 1).

Line 6 is in turn a vector with the condition since a is used as an operand, and a is the result of the condition.

This yields the following (in simplified notation):

  VEC{   i++;   loop: IF{  {i>=100}  {jump exit}  {VEC{  PAR{  {a=a*i}  {i++} }; jump loop  }  }   };   exit: q=p/a  }

The contents of VEC{ } and PAR{ } may be considered as purely combinatory networks.

VEC and PAR are preferably designed as a Petri network to control further processing after complete processing of the particular contents, as is preferred.

Due to the possibility of considering VEC and PAR as a purely combinatory network, it becomes necessary to ensure the state of the loop. In other words, in this case it is in fact necessary to create a finite automaton.

The instruction REG{ } stores variables in a register to this end. Thus, a finite automaton which is constructed exactly according to the algorithm is obtained due to the use of the combinatory networks VEC and PAC in conjunction with the register REG:

  VEC{  i++;  loop: IF{ {i>=100} {jump exit} {VEC{ PAR{ {a=a*i} {i++} }; REG{a:i} jump loop } }  };  exit: q=p/a }

It should be pointed out in particular that in PACT XPP's VPU technology (see PACT21) input and/or output registers are provided on the PAEs, the chronological correctness and the availability of data are ensured by an integrated handshake protocol (RDY/ACK). To this extent, the requirement of having their internal data processing concluded preferably on leaving VEC{ } or PAR{ } is automatically met for all variables to be used subsequently (if data processing were not concluded, the subsequent computation steps would wait for the end and the arrival of the data). Oscillating feedback is also ruled out due to the integrated registers.

To this extent, the following term is correct for this technology:

  VEC{PAR{{a=a*i}{i++}}; jump loop}

For other technologies which do not have the aforementioned embodiments or have them only partially, the term should be formulated as follows:

  VEC{PAR{{a=a*i}{i++}}; REG{a,i}; jump loop}

It should be pointed out that this form also results in correct and optimum mapping of the algorithm onto the reconfigurable processor in the applicant's VPU technology.

REG may be used within combinatory networks VEC and PAR. Strictly considered, VEC and PAR thus lose the property of combinatory networks. Abstractly, however, REG may be regarded as a complex element (REG element) of a combinatory network on which a processing time of its own is based. Processing of the following elements is made dependent on termination of computation of the REG element.

With an awareness of this conceptual inaccuracy, use of REG within VEC and PAR is allowed hereinafter and may also be necessary in particular.

As already mentioned above, use of REG is typically not necessary within a configuration of a VPU of the applicant, but is generally always explicitly necessary when the computation results of a configuration are stored so that REG in fact corresponds to the explicit register of a finite automaton in this application case.

In addition to synthesis of finite automatons for loops, finite automatons may be necessary in another case in particular:

If an algorithm is too large to be processed completely within the PAEs of a reconfigurable processor, it must be broken down into several subalgorithms. Each subalgorithm represents a configuration for the reconfigurable processor. The subalgorithms are configured in succession, i.e., sequentially on the processor, the results of the preceding configuration(s) being used as operands for the particular new configuration.

In other words, the reconfiguration results in a finite automaton which processes and stores data at a point in time t, and processes, differently if necessary, and re-stores the stored data at a point in time t+1, possibly after reconfiguration. It is essential that t is not defined in the traditional sense by clock pulses or instructions but instead by configurations. Reference is made here in particular to the processor model presentation (PACT, October 2000, San Jose).

In other words, a configuration includes a combinatory network of VEC and/or PAR the results of which are stored (REG) for further use in the next configuration:

Configuration 1: VEC{Operands;{VEC|PAR};REG{Results1}} Configuration 2: VEC{Results1;{VEC|PAR};REG{Results2}} ...

For the sake of simplicity, the above examples and descriptions have introduced the constructs VEC, PAR and REG into the high-level languages and structured them accordingly. Typically and preferably, this structuring is only performed at the level of the intermediate language (see Principles of Compiler Design (Red Dragon), Aho, Sethi, Ullmann).

It should be pointed out in particular that the structuring of algorithms using VEC, PAR and

REG is typically performed completely automatically by the compiler by methods such as graph analysis, for example.

In particular, however, it is also possible and to some extent advantageous to permit the programmer himself to structure in the high-level language by permitting VEC, PAR and REG to be written to directly in the high-level language as described above.

Generation

Automatic generation of VEC, PAR, and REG may be performed at different levels of a compilation operation. The most enlightening initially is described during a preprocessor run on the basis of the source code as in the preceding examples. However, a particularly adapted compiler is then necessary for further compilation.

Another aspect is that compilers usually perform automatic code optimization (e.g., in loops). Therefore, an efficient breakdown of the code is advisable only after the optimization runs, in particular when compilers (such as SUIF, University of Stanford) are already optimizing the code for parallelization and/or vectorization.

The particularly preferred method is therefore to tie the analyses into the back end of a compiler. The back end translates a compiler-internal data structure to the instructions of a target processor.

Pointer structures such as DAGs/GAGs, trees or 3-address codes are usually used as the compiler-internal data structures (see Principles of Compiler Design (Red Dragon), Aho, Sethi, Ullmann). Stack machine codes are also used to some extent (see Compiler selbstgeschneidert [Compiler self-tailored] CT, 1986 1-5). Since the data formats are equivalent in principle and may be transformed into one another, the preferred method according to the present invention is based on further processing of graphs, preferably trees.

Data dependencies and possible parallelisms corresponding to the method described above may be discerned automatically within trees simply on the basis of the structure. To do so, for example, known and established methods of graphic analysis may be used, for example. Alternatively or optionally, an algorithm may be analyzed for data dependencies, loops, jumps, etc. through appropriately adapted parsing methods. A method similar to the method used for analyzing expressions in compilers may be used.

Mapping

Further transformation of the algorithm now depends greatly on the target architecture. For example, the present applicant's processor architecture (VPU, XPP) offers automatic data synchronization in the hardware. This means that the correct chronological sequence of data dependencies is automatically handled in the hardware. Other architectures in some cases additionally require the synthesis of suitable state machines for controlling the data transfer.

Handling of conditional jumps is particularly interesting. For example, the present applicant's processor architecture makes available a plurality of mechanisms for mapping and execution:

-   1. Reconfiguration of the processor or parts of the processor by a     higher-level configuration unit (see, e.g., patent application(s)     PACT01, 04, 05, 10, 13, 17) -   2. Rolling out the function into the array of PAEs (see, e.g.,     patent application PACT08), where both possible branches of a     comparison are mapped onto the array at the same time, for example. -   3. Wave reconfiguration, as described in, e.g., patent     application(s) PACT08, 13, 17; a token is attached to the data to be     processed differently, and the token selects the particular valid     configuration.

It should be pointed out that mechanism number 1 is in general the case typically to be used. Mechanism 2 is already very complex with most technologies or it is not even implementable, and case 3 is so far known only from the VPU technology of the present applicant.

The execution method to be selected in each case will depend on the complexity of the algorithm, the required data throughput (performance) and the precise embodiment of the target processor (e.g., the number of PAEs).

EXAMPLES

A simple comparison should compute the following:

  if i < 0 then a=a*(−i) else a=a*i

Reconfiguration of the processor (mechanism 1) depending on the result of the comparison seems to be less appropriate. It is basically possible to roll out both branches into the array (mechanism 2). Depending on the result of the comparison, the PAEs computing either a=a*(−i) or a=a*i are triggered (see PACT08).

It is particularly efficient in terms of space to superimpose the two computations (mechanism 3) so that after the comparison, the same PAEs continue to process the data regardless of the result, but the data is provided with a token which then selects either the function a=a*(−i) or a=a*i locally in the data processing PAEs which follow the latter as a function of the result of the comparison (see, e.g., PACT08, 13, 17).

According to mechanism 1, there is a globally relevant state because the complete subsequent configuration depends on it.

According to mechanisms 2 and 3, there is only a locally relevant state, because it is no longer needed beyond the computation, which is completely implemented.

In other words, the local or global relevance of states may also depend on selected mapping onto the processor architecture.

A state which is relevant beyond a configuration and thus beyond the combinatory network of the finite automaton representing a configuration (i.e., needed by subsequent finite automatons) may basically be considered as global. The diffuse terminology of the tend combinatory network as used here should also be pointed out.

Instruction Model of the Resulting Processor

According to the present invention, there is a processor model for reconfigurable processors which includes all the essential instructions:

Arithmetic/logic instructions are mapped directly into the combinatory network. Jumps (jump/call) are either rolled out directly into the combinatory network or are implemented by reconfiguration. Condition and control flow instructions (if, etc.) are either completely resolved and processed in the combinatory network or are relayed to a higher-level configuration unit which then executes a reconfiguration according to the resulting status. Load/store operations are preferably mapped into separate configurations and are implemented by address generators similar to the known DMAs which write internal memories (REG{ }) into external memories by using address generators or which load them from external memories and/or peripherals. However, they may also be configured and operate together with the data processing configuration. Register move operations are implemented in the combinatory network by buses between the internal memories (REG{ }).

PUSH/POP operations are implemented by separate configurations which optionally write to certain internal registers in the combinatory network and/or the internal memories (REG{ }) via address generators into external memories or read out of external memories and are preferably executed before or after the actual data processing configurations.

5. DESCRIPTION OF THE FIGURES

The following figures show examples of implementation and exemplary embodiments of the compiler.

FIG. 1 a shows the design of an ordinary finite automaton in which a combinatory network (0101) is linked to a register (0102). Data may be sent directly to 0101 (0103) and 0102 (0104). Processing of a state as a function of the preceding state(s) is possible via feedback (0105) from the register to the combinatory network. The processing results are represented by 0106.

FIG. 1 b shows a representation of the finite automaton by a reconfigurable architecture according to PACT01 and PACT04 (PACT04 FIGS. 12 through 15). The combinatory network from FIG. 1 a (0101) is replaced (0101 b) by a system of PAEs 0107. Register (0102) is implemented by a memory (0102 b) which is capable of storing a plurality of cycles. The feedback according to 0105 takes place via 0105 b. Inputs (01013 b and/or 0104 b) are equivalent to 0103 and 0104, respectively. Direct access to 0102 b may be implemented via a bus through array 0101 b, if necessary. Output 0106 b is in turn equivalent to 0106.

FIG. 2 shows the mapping of a finite automaton onto a reconfigurable architecture. 0201(x) represents the combinatory network (which may be designed as PAEs according to FIG. 1 b). There exist one or more memories for operands (0202) and one or more memories for results (0203). Additional data inputs according to 0103 b, 0104 b, 0106 b are not shown for the sake of simplicity. An address generator (0204, 0205) is assigned to each memory.

Operand and results memories (0202, 0203) are physically or virtually interlinked so that the results of a function and/or an operation may be used as operands for another function and/or operation, for example, and/or both results and newly added operands of one function may be used as operands for another function. Such a linkage may be established, for example, by bus systems or by (re)configuration through which the function and interconnection of the memories with the 0201 is reconfigured.

FIG. 3 shows different aspects for handling variables.

In FIGS. 3 a, 0301, 0302 and 0303 indicate different stages of the computation. These stages may be purely combinatory or they may be separated via registers, where f1, f2, f3 are functions, x1 is a variable according to the patent description.

FIG. 3 b shows the use of a variable x1 in the function x1:=x1+1.

FIG. 3 c shows the behavior of a finite automaton for computation of x1:=x1+1 within a configuration. In the next configuration, 0306 and 0304 are to be switched around in order to obtain a complete finite automaton. 0305 represents the address generators for memories 0304 and 0306.

FIG. 4 shows implementations of loops. The modules shown as hatched may be generated by macros (0420, 0421). 0421 may be inserted by analysis of the graph at occurrences of undelayed feedback.

FIG. 4 a shows the implementation of a simple loop of the type

  WHILE TRUE DO  x1 := x1 + 1;

At the core of the loop is counter+1 (0401). 0402 is a multiplexer which at the beginning supplies the starting value of x1 (0403) to 0401 and then causes feedback (0404 a, 0404 b) with each iteration. A register (see REG{ }) (0405) is used in the feedback to prevent undelayed and thus uncontrolled feedback of the output of 0401 to its input. 0405 is pulsed with the working clock pulse of the VPU and thus determines the number of iterations per unit of time. The particular count could be picked up at 0404 a or 0404 b. Depending on the definition of the high-level language, however, the loop does not terminate. For example, the signal at 0404 would be useful in an HDL (according to the related art (e.g., VHDL, Verilog)), whereas 0404 it is not usable in a sequential programming language (e.g., C) because the loop does not terminate and thus does not yield any exit value.

Multiplexer 0402 implements a macro formed from the loop construct. This macro is instantiated by the translation of WHILE.

Register 0405 is either also part of the macro or is inserted according to a graphic analysis according to the related art exactly at the location and time where there is undelayed feedback in order to thus suppress the vibration tendency.

FIG. 4 b shows the design of a true loop of the type

  WHILE xl < 10 DO  x1 := x1 + 1;

This design corresponds essentially to FIG. 4 a, which is why the same references have been used.

In addition, a circuit is shown which checks on the validity of the results (0410) and relays the signal of 0404 a to the downstream functions (0411) only when the abortion criterion of the loop has been reached. The abortion criterion is determined by the comparison x1<10 (comparison stage 0412). As a result of the comparison, the particular status flag (0413) is sent to a multiplier means 0402 for controlling the loop and functions 0411 for controlling the forwarding of results. Status flag 0413 may be implemented, for example, by triggers described in German Patent Application No. DE 197 04 728.9. Likewise, status flag means 0413 may be sent to a CT which then recognizes that the loop has been terminated and performs a reconfiguration.

FIG. 5 a shows the iterative computation of

  FOR i:=1 TO 10  x1 := x1 * x1;

The basic function corresponds to that in FIG. 4 b, which is why the same references have also been used here. Function block 0501 computes the multiplication. The FOR loop is then implemented by another loop according to FIG. 4 b and is indicated only by block 0503. Block 0503 supplies the status of the comparison to the abortion criterion. The status is used directly for triggering the iteration, thus largely eliminating means 0412 (represented by 0502).

FIG. 5 b shows the rolling out of the computation of

  FOR i:=1 TO 10  x1 := x1 * x1;

Since the number of iterations at translation time is known exactly, the computation may be mapped into a sequence of i multipliers (0510).

FIG. 6 shows the execution of a WHILE loop according to FIG. 4 b over several configurations. The state of the loop (0601) here is a relevant state because it has a significant influence on the function in the subsequent configurations. The computation extends over four configurations (0602, 0603, 0604, 0605). Between the configurations, the data is filed in memories (see REG{ }) (0606, 0607). 0607 also replaces 0405.

The filling level of the memories may be used as a reconfiguration criterion as indicated via 0606, 0607: memory full/empty and/or 0601 which indicates abortion of the loop. In other words, the filling level of the memories generates triggers (see, e.g., PACT01, PACT05, PACT08, PACT10) which are sent to the configuration unit and trigger a reconfiguration. The state of the loop (0601) may also be sent to the CT. The CT may then configure the subsequent algorithms on reaching the abortion criterion and/or may first process the remaining parts of the loop (0603, 0604, 0605) and then load the subsequent configurations.

6. PARALLELIZABILITY

FIG. 6 shows potential limits to parallelizability.

If computation of the operands is independent of feedback 0608, the loop may be computed in blocks, i.e., by filling memories 0606/0607 each time. This achieves a high degree of parallelism.

If computation of an operand depends on the result of the previous computation, i.e., feedback 0608 or the like enters into the computation, the method is less efficient because it is possible to compute only one operand within the loop.

If the usable ILP (instruction level parallelism) within the loop is high and the time for reconfiguration is short (see, e.g., PACT02, PACT04, PACT13, PACT17), a computation rolled out on PAEs may also be efficient on a VPU.

If this is not the case, it is appropriate to map the loop onto a sequential architecture (processor separate from the PA or implementation within the PA described in DE 196 51 075.9-53, DE 196 54 846.2-53, and in particular DE 199 26 538.0 (FIGS. 5, 11, 16, 17, 23, 30, 31, 33)).

Analysis of the computation times may be performed in the compiler at translation time according to the following section and/or it may be measured empirically at run time or at a run time to induce a subsequent optimization, which results in a compiler capable of learning, in particular a self-learning compiler.

Analytical methods and parallelization methods are important for the present invention.

Various methods according to the related art are available for analysis and implementation of the parallelization.

A preferred method is described below.

Functions to be mapped are represented by graphs (see, e.g., PACT13; DE 199 26 538.0); an application may be composed of any number of different functions. The graphs are analyzed for the parallelism they contain; all optimization methods may be used in advance.

For example, the following tests are to be performed:

6.0.1 ILP (Instruction Level Parallelism)

ILP expresses which instructions may be executed simultaneously (see PAR{ }). Such an analysis is easily possible on the basis of the consideration of dependencies of nodes in a graph. Similar methods are known sufficiently well from the related art and mathematics per se, and reference shall be made to VLIW compilers and synthesis tools as examples.

However, conditional, possibly nested, executions (IF), for example, deserve special attention because a correct statement regarding the paths to be executed simultaneously is often impossible or hardly possible because there is a strong dependence on the value space of the individual parameters, which is often known only inadequately or not at all. Furthermore, an exact analysis may take so much computation time that it may no longer be reasonably performed.

In such cases, the analysis may be simplified by instructions from the programmer, for example, and/or it is possible to operate on the basis of corresponding compiler switches so that in case of doubt either high parallelizability is to be assumed (possibly squandering resources) or low parallelizability is to be assumed (possibly squandering performance).

In these cases, an empirical analysis may also be performed at run time. PACT10, PACT17, described methods which make it possible to compile statistics regarding the program behavior at run time. It is thus possible to initially assume maximum parallelizability, for example. The individual paths return messages to a statistics unit (e.g., implemented in a CT or some other stage, see, e.g., PACT10, PACT17, but basically also units according to PACT04 may be used) regarding each run cycle. Using statistical measures, it is now possible to analyze which paths are actually run through simultaneously. In addition, there is also the possibility of evaluating which paths are run through simultaneously frequently or rarely or never, based on the data at run time. This type of path usage message is not obligatory but is advantageous.

Accordingly, the execution may be optimized in a next program call. It should be pointed out that the statistics information may not be written away in particular in a nonvolatile manner as on a hard drive. PACT22, PACT24 described that either a plurality of configurations may be configured simultaneously and then triggered by triggers (PACT08) or only a subset may be configured, the remaining configurations being loaded subsequently as necessary by sending the corresponding triggers to a loading unit (CT, PACT10).

Value PAR(p) which is used below indicates for the purpose of clarification which parallelism is achievable on an instruction level, i.e., how many ILPs may be achieved at a certain stage (p) within the data flow graph transformed from the function (FIG. 7 a).

Vector parallelism is also significant (see VEC{ }). Vector parallelism is useful when large volumes of data must be processed. In this case, linear sequences of operations are vectorizable, i.e., all operations may process data at the same time, typically with each separate operation processing a separate data word.

Within loops, this procedure may be impossible to some extent. Analyses and optimizations are therefore necessary. For example, the graph of a function may be expressed by a Petri network. Petri networks have the property that forwarding of results is controlled by nodes so that loops may be modeled, for example. Data throughput is determined by the feedback of the result in a loop. Examples:

-   -   The result of computation n is needed for computation n+1: only         one computation may be executed within the loop.     -   The result of computation n is needed for computation n+m: m−1         computations may be executed within the loop.     -   The result determines the abort of the loop, but it does not         enter into the computation of the results: no feedback is         necessary. Although incorrect values (too many values) enter the         loop under some circumstances, the output of results may be         interrupted directly on reaching the end condition at the end of         the loop.

Before the analysis of loops, they may be optimized according to the related art. For example, certain instructions may be extracted from the loop and placed before or after the loop.

Value VEC which is used below for clarification may illustrate the degree of vectorizability of a function. In other words, VEC indicates how many data words may be processed simultaneously within a set of operations. For example, VEC may be computed from the number of required arithmetic means for a function n_(nodes) and data n_(data) calculable within the vector at the same time, e.g., by VEC=n_(nodes)/n_(data).

If a function may be mapped onto five arithmetic means (n_(nodes)=5), for example, and if data may be processed at the same time in each of the arithmetic means (n_(data)=5), then VEC=1 (FIG. 7 b).

However, if a function may be mapped onto five arithmetic means (n_(nodes)=5) and data may be processed in only one arithmetic means, e.g., based on feedback of the results of the pipeline back to the input (n_(data)=5), then VEC=1/5 (FIG. 7 c).

VEC may be computed for an entire function and/or for partial sections of a function. For the compiler according to the present invention, both variants may be advantageous, as is the case in general for determination and analysis of VEC.

According to FIG. 7 a, PAR(p) is determined for each line of a graph, as is possible in an advantageous manner. A line of a graph is defined by being executed within one clock unit. The number of operations depends on the implementation of the particular VPU.

If PAR(p) corresponds to the number of nodes in line p, then all the nodes may be executed simultaneously.

If PAR(p) is smaller, certain nodes are executed only alternatively. The alternative executions of one node are each combined in one PAE. A selection device permits activation of the alternative corresponding to the status of data processing at run time as described in PACT08, for example.

VEC is also assigned to each line of a graph. If VEC=1 for one line, this means that the line remains as a pipeline stage. If one line is less than 1, then all the following lines which are also less than 1 are combined because pipelining is impossible. They are combined according to the sequence of operations to yield a sequence which is then configured into a PAE and is processed sequentially at run time. Similar methods are described in PCT/DE 97/02949 and/or PCT/DE 97/02998, for example.

Using the method described here, any complex parallel processor models may be constructed by groups of sequencers. In particular, sequencer structures may be generated for mapping reentrant code.

The synchronizations required to accomplish this may be implemented, for example, by the time stamp method described in PACT18 or preferably by the triggering method described in PACT08.

If a plurality of sequencers or sequential parts is mapped onto a PA, then it is preferable to coordinate the power of individual sequencers for power consumption reasons. This may be accomplished in a particularly preferable manner by adapting the working frequencies of the sequencers to one another. For example, methods which allow individual clocking of individual PAEs or groups of PAEs are described in PACT25 and PACT18.

The frequency of a sequencer may be determined on the basis of the number of cycles typically needed for processing the function assigned to it.

For example, if it needs five clock cycles for processing its function while the remaining system needs exactly one clock cycle to process assigned tasks, then its clocking should be five times faster than the clocking of the remaining system. In the case of a plurality of sequencers, different clock cycles are possible. A clock multiplication and/or a clock division may also be provided.

Functions are partitioned according to the aforementioned method. In partitioning, memories for data and relevant status are inserted accordingly. Additional alternative and/or extended methods are described in PACT13 and PACT18.

According to PACT01, PACT10, PACT13, PACT17, PACT22, PACT24, some VPUs offer the possibility of differential reconfiguration. This may be used if only relatively few changes are necessary within the system of PAEs in a reconfiguration. In other words, only the changes in a configuration in comparison with the existing configuration are reconfigured. Partitioning in this case may be such that the (differential) configuration following a configuration contains only the required reconfiguration data and does not constitute a complete configuration. The compiler of the present invention is preferably designed to recognize and support this.

Scheduling of the reconfiguration may be performed through the status which reports function(s) to a loading unit (CT) which in turn selects on the basis of the incoming status the next configuration or partial configuration and configures it. Such methods are described in detail in PACT01, PACT05, PACT10, PACT13, PACT17.

In addition, scheduling may support the possibility of preloading configurations during the run time of another configuration. A plurality of configurations may also be preloaded speculatively, i.e., without knowing whether the configurations are needed at all. This is preferred in particular when the CT is at least largely without load and in particular has little or no task load, e.g., in the case of lengthy data streams that are processable without configuration. Due to the selection mechanisms such as those described in DE 197 04 728.9, for example, the configurations to be used are then selected at run time (see also example NLS in PACT22/24).

The local sequencers may likewise be controlled by the status of their data processing as is known, for example, from DE 196 51 075.9-53, DE 196 54 846.2-53, DE 199 26 538.0. To perform their reconfiguration, another dependent or independent status may be reported to the CT (see PACT04, LLBACK, for example).

The present invention will now be described with reference to additional figures, the following characters being used below to simplify the notation: ω or, ω and.

FIG. 8 a shows the graph according to FIG. 7 a mapped on a group of PAEs at maximum achievable parallelism. All operations (instructions i1-i12) are mapped into individual PAEs.

FIG. 8 b shows the same graphs, e.g., with maximum usable vectorizability, but the sets of operations V2={i1, i3}, V3={i4, i5, i6, i7, i8}, V4={i9, i10, i11} are not parallel par (par({2,3,4})=1). This makes it possible to save on resources by assigning one set P2, P3, P4 of operations to one PAE each time. A status signal for each data word in each stage selects the operation to be executed in the particular PAE. The PAEs are interconnected as a pipeline (vector) and each PAE executes one operation on a different data word per each clock cycle.

This yields the following sequence:

PAE1 computes data and sends it to PAE2. Together with the data, it forwards a status signal which indicates whether i1 or i2 is to be executed. PAE2 continues to compute the data of PAE1. The operation to be executed (i1, i2) is selected and computed according to the incoming status signal. According to the computation, PAE2 forwards a status signal to PAE3, indicating whether (i4ωi5) ω (i6ωi7ωi8) is to be executed. PAE3 continues to compute the data of PAE2. The operation to be executed (i4ωi5) ω(i6ωi7ωi8) is selected and computed according to the incoming status signal. As a result of the computation, PAE3 forwards a status signal to PAE4, indicating whether i9ωi10ωi11 is to be executed. PAE4 continues to compute the data of PAE3. The operation to be executed (i9ωi10ωi11) is selected and computed according to the incoming status signal. PAE5 continues to compute the data of PAE4.

One possible similar method and hardware which allow a particularly favorable implementation of the method described here are described in DE 197 04 728.9 (FIGS. 5 and 6). PACT04 and PACT10, PACT13 also describe methods that may be used in general but are more complex.

FIG. 8 c again shows the same graph. In this example, vectorization is impossible but PAR(p) is high, which means that a plurality of operations may be executed within one line at the same time. The operations to be implemented in parallel are P2={i1 ωi2}, P3={i4 ωi5 ωi6 ωi7 ωi8}, P4={i9 ωi10 ωi11}. The PAEs are interconnected so that they may exchange any data among themselves in any way. The individual PAEs perform operations only when there is an ILP in the corresponding cycle; otherwise they behave neutrally (NOP), and there may optionally be a clocking down and/or a clock shutdown and/or a current shutdown to minimize power loss.

The following sequence is provided:

In the first cycle, only PAE2 operates and forwards data to PAE2 and PAE3.

In the second cycle, PAE2 and PAE3 are operating in parallel and forward data to PAE1, PAE2, PAE3, PAE4, PAE5.

In the third cycle, PAE1, PAE2, PAE3, PAE4 and PAE5 are operating and forward data to PAE2, PAE3 and PAE5.

In the fourth cycle, PAE2, PAE3 and PAE5 are operating and forward data to PAE2.

In the fifth cycle, only PAE2 is operating.

This function thus requires five cycles for the computation. The corresponding sequencer should thus operate with a five-fold clock cycle in relation to its environment in order to achieve a similar performance.

A possible similar method is described in PACT02 (FIGS. 19, 20 and 21). PACT04 and PACT10, PACT13 also describe methods that may be used in general but are more complex. Additional methods and/or hardware may also be used.

FIG. 8 d shows the graphs according to FIG. 7 a in the case where there is no usable parallelism. To compute a data word, each stage must be run through in succession. Within the stages only one of the branches is always processed.

The function also requires five cycles for the computation: cy1=(i1), cy2=(i2ωi3), cy3=(i4ωi5ωi6ωi7ωi8), cy4=(i9ωi10ωi11), cy5=(i12). Thus the corresponding sequencer should work with a clock cycle five times faster in relation to its environment to achieve a similar performance.

Such a function is mappable, for example, as in FIG. 8 c by using a simpler sequencer according to PACT02 (FIGS. 19, 20 and 21). PACT04 and PACT10, 13 also describe methods that may be used in general but are more complex.

The illustrations represented in FIG. 8 may be combined and grouped at will.

In FIG. 9 a, for example, the same function is shown in which the paths (i2 ω(i4ωi5) ωi9) and (i3 ω(i6ωi7ωi8) ω(i9ωi10)) are executable simultaneously. (i4ωi5), (i6ωi7ωi8), (i9ωi10) are each alternatives. The function is also vectorizable. It is thus possible to construct a pipeline in which the particular function to be executed is determined on the basis of status signals for three PAEs (PAE4, PAE5, PAE7).

FIG. 9 b shows a similar example in which vectorization is impossible. However, the paths (i1 ωi2 ω(i4ωi5) ωi9 ωi12) and (i3 ω(i6ωi7ωi8) ω(i10ωi11)) are parallel. Optimum performance may thus be achieved by using two PAEs which also process the parallel paths simultaneously. The PAEs are synchronized with one another by status signals which are generated preferably by PAE1 because it computes the start (i1) and the end (i12) of the function.

It should be pointed out in particular that a symmetrically parallel processor model (SMP) or the like could yield the multiprocessor models in use today by a multiple array of sequencers.

It should also be pointed out that all configuration registers for scheduling may also be loaded with new configurations in the background and/or during data processing.

This is possible if the hardware has the design described in DE 196 51 075.9-53, for example. Independent memory areas or registers are then available and may be addressed independently. It is possible to jump to certain locations due to incoming triggers; jump instructions (JMP, CALL/RET) are also possible and may also be executed conditionally, if necessary.

As described in DE 196 54 846.2-53, independent read and write pointers are available, so that basically there is independence and thus the possibility of access in the background. In particular, it is possible to partition the memories, thus providing additional independence.

Jumps are possible via jump instructions (JMP, CALL/RET) which may also be executed conditionally if necessary.

As described in DE 197 04 728.9, the individual registers which may be selected by the triggers are basically independent and therefore allow independent configuration in particular in the background. Jumps within the register are not possible, and selection is made exclusively via the trigger vectors.

An important factor for evaluating the efficiency of PAR and VEC may be the type of data processed by the particular structure. For example, it is worthwhile to roll out a structure, i.e., to pipeline or parallelize a structure which processes a large volume of data, as is the case with video data or telecommunications data, for example. It is not worthwhile to roll out structures which process low data volumes (e.g., keyboard input, mouse, etc.); on the contrary, they would block resources for other algorithms.

Thus it is proposed that only the algorithms, structures or parts of algorithms which appropriately process large volumes of data shall be parallelized and vectorized on the basis of different instructions.

Such instructions might be, for example:

1. The data type (On the basis of the higher data volume, arrays, streams should be rolled out with preference over individual characters, for example). 2. The type of access (linear program sequences should be mapped into sequencers, for example, whereas it is worthwhile to roll out loops because of the high number of runs, for example). 3. The type of source and/or the target (keyboard and mouse, for example, have a data rate that is too low to be rolled out efficiently, but the data rate of a network, for example, and/or video sources or targets is much higher).

Any set of these instructions may be used for analysis.

7. DEFINITION OF TERMS

locally relevant state state that is relevant only within a certain configuration; globally relevant state state that is relevant in multiple configurations and must be exchanged among configurations; relevant state state that is needed within an algorithm for correct execution thereof and is thus described and used by the algorithm; irrelevant state state that is not important for the actual algorithm and is also not described in the algorithm but is needed by the executing hardware, depending on the implementation. 

1-20. (canceled)
 21. A method for compiling high-level software programs into instruction level parallel code, comprising: generating a code graph; in a first analysis, analyzing the code graph for instructions that are simultaneously executable at a same level of the code graph; in a second analysis, analyzing the code graph for instructions being simultaneously executable at different levels of the code graph; and partitioning the code graph depending on the first and second analyses.
 22. The method according to claim 21, wherein the partitioning includes mapping of parts of the code graph onto sequential processing units.
 23. The method according to claim 22, wherein at least some of the sequential processing units are horizontally connected and operate on commonly received data input.
 24. The method according to any one of claims 22 and 23, wherein at least some of the sequential processing units are vertically connected, and each of at least one of the sequential processing units operates on data received from at least one other of the sequential processing units.
 25. The method according to claim 24, wherein code for a reconfigurable processor is produced by the method.
 26. The method according to claim 24, wherein code for a field programmable gate array (FPGA) is produced by the method.
 27. The method according to claim 24, wherein code for a central processing unit (CPU) is produced by the method.
 28. The method according to claim 24, wherein code for a parallel processor system is produced by the method.
 29. The method according to any one of claims 21 to 23, wherein code for a reconfigurable processor is produced by the method.
 30. The method according to any one of claims 21 to 23, wherein code for a field programmable gate array (FPGA) is produced by the method.
 31. The method according to any one of claims 21 to 23, wherein code for a central processing unit (CPU) is produced by the method.
 32. The method according to any one of claims 21 to 23, wherein code for a parallel processor system is produced by the method. 